Image Forming Apparatus and Image Forming System

ABSTRACT

An image forming apparatus contains: an internal device that performs a service; a message processing unit that parses a message according to service definition data, the service definition data including syntax definitions of an interface part of the service and designation of a protocol to be used for the service; and a control unit that controls the internal device according to a request obtained from a result of parsing the message by the message processing unit in order to execute the service.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application relates to and claims priority rights from JapanesePatent Applications:

(1) Japanese Patent Application No. 2008-181641, filed on Jul. 11, ,2008

(2) Japanese Patent Application No. 2008-181642, filed on Jul. 11, ,2008

(3) Japanese Patent Application No. 2008-211766, filed on Aug. 20, 2008

(4) Japanese Patent Application No. 2007-253070, filed on Sep. 28, 2007

(5) Japanese Patent Application No. 2007-253071, filed on Sep. 28, 2007

(6) Japanese Patent Application No. 2007-253073, filed on Sep. 28, 2007

(7) Japanese Patent Application No. 2007-253074, filed on Sep. 28, 2007

(8) Japanese Patent Application No. 2007-253072, filed on Sep. 28, 2007

(9) Japanese Patent Application No. 2007-253075, filed on Sep. 28, 2007

(10) Japanese Patent Application No. 2007-253076, filed on Sep. 28, 2007

(11) Japanese Patent Application No. 2007-253077, filed on Sep. 28, 2007

(12) Japanese Patent Application No. 2007-270788, filed on Oct. 18, 2007

(13) Japanese Patent Application No. 2007-270786, filed on Oct. 18, 2007

(14) Japanese Patent Application No. 2007-270787, filed on Oct. 18, 2007

(15) Japanese Patent Application No. 2007-270784, filed on Oct. 18, 2007

(16) Japanese Patent Application No. 2007-270785, filed on Oct. 18, 2007

(17) Japanese Patent Application No. 2007-281541, filed on Oct. 30, 2007

the entire disclosures of which are hereby incorporated by referenceherein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to image forming apparatus and image formingsystem.

2. Description of the Related Art

In a direction text for operating an image forming apparatus, directionsfor performing services are described in XML (Extensible MarkupLanguage). In a system, the direction texts have been stored in a serverdevice, and upon selecting one of the direction texts, one or moreservices described in the selected direction text are performed by oneor more job executing devices. In the direction text described in XML,setting parameters can be described.

An image forming apparatus such as multi function peripheral has anoperation panel that contains a display device and an input device. Thisdisplay device displays a user interface screen. The user interfacescreen mainly has components such as button. The user interface screenis displayed in terms of program control. In general, a program isgenerated by compiling a source file described in a programming languagesuch as C or Java with API (Application Program Interface) in the imageforming apparatus. The program has been stored in advance as anexecutable program.

SUMMARY OF THE INVENTION

In case that the direction texts have been stored, if sorts ofparameters, the number of parameters, permissible values of parameters,or the like want to be changed, all direction texts related to thechange have to be re-generated and stored. Further, communicationprocedures and formats of messages for transmitting/receiving thedirection text are pre-defined and used between devices. Therefore, ifthe communication procedures and the formats of messages want to bechanged, designs of the devices have to be changed considerably.

Furthermore, a program for displaying a user interface screen isgenerated by compiling a source file described in a programminglanguage. Therefore, in order to customize the user interface screen, adevelopment environment is necessary to generate an executable programfrom a source program in the programming language, and it is difficultfor other people than programmers to change the source file.

This invention has been made in view of the aforementionedcircumstances. It is an object of the present invention to provide animage forming apparatus in which significant changes are not necessaryeven if a specification of messages used for services is changed. Inaddition, it is an object of the present invention to provide an imageforming apparatus and an image forming system in which a user interfacescreen can be customized easily.

The present invention solves these subjects as follows.

An image forming apparatus according to an aspect of the presentinvention contains: an internal device that performs a service; amessage processing unit that parses a message according to servicedefinition data, the service definition data including (a) syntaxdefinitions of an interface part of the service and (b) designation of aprotocol to be used for the service; and a control unit that controlsthe internal device according to a request obtained from a result ofparsing the message by the message processing unit in order to performthe service.

In this apparatus, messages are parsed according to the servicedefinition data. Therefore, a specification of the messages can bechanged by changing the service definition data. In the servicedefinition data, (a) syntax definitions of an interface part of aservice and (b) designation of a protocol to be used for the service aredescribed separately. Thus, it is possible to change a specification ofmessages without changing the interface part to be used to call theservice. Significant changes in the apparatus are not required to changea specification of messages used for services.

Further, the aforementioned image forming apparatus may contain areceiving unit that receives the message via a computer networkaccording to a communication protocol, and the message processing unitparses the message received by the receiving unit.

Further, in the aforementioned image forming apparatus, the messageprocessing unit may generate a message indicating a result of theservice according to the service definition data.

In this apparatus, messages are generated according to the servicedefinition data. Therefore, a specification of the messages can bechanged by changing the service definition data. In the servicedefinition data, (a) syntax definitions of an interface part of aservice and (b) designation of a protocol to be used for the service aredescribed separately. Thus, it is possible to change a specification ofmessages without changing the interface part to be used to call theservice. Significant changes in the apparatus are not required to changea specification of messages used for services.

Further, the aforementioned image forming apparatus may contain areceiving unit that receives a message via a computer network accordingto a communication protocol, and a transmitting unit that transmits amessage via the computer network; the message processing unit may parsea message received by the receiving unit; the message processing unitmay generate a message indicating a result of the service performedaccording to a request obtained from a result of parsing the messagereceived by the receiving unit; and the transmitting unit may transmitthe message generated by the message processing unit.

Further, in the aforementioned image forming apparatus, the protocoldesignated in the service definition data may be SOAP, the receivingunit may receive the message according to HTTP, and the transmittingunit may transmit the message according to HTTP.

Further, in the aforementioned image forming apparatus, the servicedefinition data may be XML data described in WSDL.

Further, in the aforementioned image forming apparatus, the servicedefinition data may include schema data, the schema data includes syntaxdefinitions of the message to be received or transmitted, and themessage processing unit may parse the message according to the servicedefinition data and the schema data.

Therefore, it is possible to change a specification of messages bychanging the schema data without changing the interface part used tocall a service.

Further, in the aforementioned image forming apparatus, the servicedefinition data may include a reference to schema data, and the messageprocessing unit may read out the schema data with the reference andparse the message according to the service definition data and theschema data.

Therefore, it is possible to change a specification of messages bychanging the schema data without changing the interface part used tocall a service.

Further, in the aforementioned image forming apparatus, the servicedefinition data may be XML data described in WSDL, and the schema datamay be XML data described in XML Schema.

An image forming system according to an aspect of the present inventioncontains: a terminal device connected to a computer network, and animage forming apparatus that is connected to the computer network andexecutes one or more services according to a request that occurs in theterminal device. The image forming apparatus comprises: a receiving unitthat receives a request message via the computer network according to acommunication protocol; an internal device that performs the one or moreservices; a message processing unit that parses the request messageaccording to service definition data and schema data; and a control unitthat controls the internal device according to a request obtained from aresult of parsing the request message by the message processing unit inorder to perform the service. The service definition data includes (a)syntax definitions of an interface part of the service and (b)designation of a protocol to be used for the service, and the schemadata includes syntax definitions of the message. The terminal deviceobtains the service definition data and/or the schema data from theimage forming apparatus, generates and transmits the request message tothe image forming apparatus according to the service definition dataand/or the schema data.

In this system, messages are parsed according to the service definitiondata. Therefore, a specification of the messages can be changed bychanging the service definition data. In the service definition data,(a) syntax definitions of an interface part of a service and (b)designation of a protocol to be used for the service are describedseparately. Thus, it is possible to change a specification of messageswithout changing the interface part to be used to call the service.Significant changes in the apparatus are not required to change aspecification of messages used for services. Moreover, the terminaldevice obtains the service definition data and/or schema data from theimage forming apparatus that performs a service, and consequently theservice definition data and/or schema data are/is not necessary to bestored in the terminal device in advance.

Further, in the aforementioned image forming system, the terminal devicemay distill permissible values of a parameter from the servicedefinition data and/or the schema data, select one of the permissiblevalues as a value of the parameter, and generate the request messageincluding the value of the parameter.

Therefore, permissible values of the parameter are not necessary to bestored in the terminal device in advance.

Further, in the aforementioned image forming system, the image formingapparatus may contain a transmitting unit that transmits a message viathe computer network according to the communication protocol. Themessage processing unit of the image forming apparatus may generate aresponse message indicating a result of the service performed accordingto a request obtained from a result of parsing the request messagereceived by the receiving unit, and the transmitting unit of the imageforming apparatus transmits the response message generated by themessage processing unit, and the terminal device receives the responsemessage.

Further, in the aforementioned image forming system, the protocoldesignated in the service definition data may be SOAP, the receivingunit may receive the message according to HTTP, and the transmittingunit may transmit the message according to HTTP.

Further, in the aforementioned image forming system, the servicedefinition data may be XML data described in WSDL.

Further, in the aforementioned image forming apparatus, the servicedefinition data may include schema data, and the message processing unitmay parse the message according to the service definition data and theschema data.

Therefore, it is possible to change a specification of messages bychanging the schema data without changing the interface part used tocall a service.

Further, in the aforementioned image forming system, the servicedefinition data may include a reference to schema data, and the messageprocessing unit may read out the schema data with the reference andparse the message according to the service definition data and theschema data.

Therefore, it is possible to change a specification of messages bychanging the schema data without changing the interface part used tocall a service.

Further, in the aforementioned image forming apparatus, the servicedefinition data may be XML data described in WSDL, and the schema datamay be XML data described in XML Schema.

An image forming apparatus according to an aspect of the presentinvention contains: a display device that displays a user interfacescreen; a data storage device that stores user interface data containingattributions of components in the user interface screen; and a UI dataparsing unit that identifies attributions of the components with parsingthe user interface data, and causes the display device to display theuser interface screen that reflects the attributions of the components.The user interface data is described as text data.

Therefore, it is possible to customize a user interface by editing userinterface data in a text format. Consequently, it is possible tocustomize a user interface screen of the image forming apparatus easily.

Further, the aforementioned image forming apparatus may contain: amessage processing unit that parses a message according to servicedefinition data; and a control unit that performs the editing serviceaccording to a request obtained from a result of parsing the message bythe message processing unit. The service definition data includes (a)syntax definitions of an interface part of an editing service of theuser interface data and (b) designation of a protocol to be used for theservice.

The image forming apparatus performs editing user interface data as aservice, and therefore, it is possible to edit user interface data bytransmitting a message from an external device to the image formingapparatus without operating the image forming apparatus directly.Consequently, it is possible to customize a user interface screen of theimage forming apparatus easily.

Further, the aforementioned image forming apparatus may contain areceiving unit that receives the message via a computer networkaccording a communication protocol, and the message processing unit mayparse the message received by the receiving unit.

Further, in the aforementioned image forming apparatus, the protocoldesignated in the service definition data may be SOAP, and the receivingunit may receive the message according to HTTP.

Further, in the aforementioned image forming apparatus, the servicedefinition data may be XML data described in WSDL.

Further, in the aforementioned image forming apparatus, the servicedefinition data may include schema data, the schema data includes syntaxdefinitions of the message to be received or transmitted, and themessage processing unit may parse the message according to the servicedefinition data and the schema data.

Further, in the aforementioned image forming apparatus, the userinterface data and the message may be described in XML, and the controlunit may update the user interface data with an XML text of theattributions of the components distilled by the message processing unit.

Therefore, conversion from a message to an XML text for the userinterface data is not necessary.

An image forming system contains: an image forming apparatus connectedto a computer network, and a terminal device connected to the computernetwork. The image forming apparatus contains: a display device thatdisplays a user interface screen; a data storage device that stores userinterface data containing attributions of components in the userinterface screen; a UI data parsing unit that identifies attributions ofthe components with parsing the user interface data, and causes thedisplay device to display the user interface screen that reflects theattributions of the components; a receiving unit that receives themessage via the computer network according to a communication protocol;a message processing unit that parses a message according to servicedefinition data, the service definition data including (a) syntaxdefinitions of an interface part of an editing service of the userinterface data and (b) designation of a protocol to be used for theservice; and a control unit that executes the editing service accordingto a request obtained from a result of parsing the message by themessage processing unit. The user interface data is described as textdata. The terminal device comprises a transmitting unit that transmitsthe message via the computer network according to a communicationprotocol.

Therefore, it is possible to customize a user interface by editing userinterface data in a text format. The image forming apparatus performsediting user interface data as a service, and therefore, it is possibleto edit user interface data by transmitting a message from an externaldevice to the image forming apparatus without operating the imageforming apparatus directly. Consequently, it is possible to customize auser interface screen of the image forming apparatus easily.

Further, in the aforementioned image forming system, the data storagedevice may store schema data including syntax definitions of themessage; the terminal device may contain a schema data obtaining unitthat obtains a part or all of the schema data from the image formingapparatus and identifies one or more items in the attributions of thecomponents with the part or all of the schema data; and the transmittingunit may transmit the message to set one or more values to a part or allof the one or more items identified by the schema data obtaining unit.

Therefore, it is possible to customize the image forming apparatuswithout storing items of the components in the terminal device inadvance.

Further, in the aforementioned image forming system, the data storagedevice may store schema data including syntax definitions of themessage; the terminal device may contain a schema data obtaining unitthat obtains a part or all of the schema data from the image formingapparatus and identifies one or more permissible values on theattributions of the components with the part or all of the schema data;and the transmitting unit may transmit the message to set a valueselected from the one or more permissible values to one of theattributions.

Therefore, it is possible to customize the image forming apparatuswithout storing attribution information of the components in theterminal device in advance.

Further, in the aforementioned image forming system, the user interfacedata and the message may be described in XML, the schema data may be XMLdata described in XML Schema, and the control unit may update the userinterface data with an XML text of the attributions of the componentsdistilled by the message processing unit.

Therefore, it is possible to customize the image forming apparatuswithout storing syntax definitions in the terminal device in advance.

Further, in the aforementioned image forming system, the data storagedevice may store template files containing respective default data ofthe user interface screen. The transmitting unit may select one of thetemplate files and transmit the message to set default data in theselected template file as data of one of user interface screens in theuser interface data.

Therefore, it is possible to execute complex customization easily withusing the templates.

These and other objects, features and advantages of the presentinvention will become more apparent upon reading of the followingdetailed description along with the accompanied drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a block diagram that indicates an image forming systemincluding a multi function peripheral as an image forming apparatusaccording to Embodiment 1 of the present invention;

FIG. 2 shows a diagram that indicates an instance of service definitiondata described in WSDL;

FIG. 3 shows a diagram that indicates an instance of schema datareferenced in service definition data;

FIG. 4 shows a diagram that indicates an instance of a request messagein Embodiment 1 of the present invention;

FIG. 5 shows a diagram that indicates an instance of a response messagein Embodiment 1 of the present invention;

FIG. 6 shows a diagram that indicates a layer structure of messagecommunication process in Embodiment 1 of the present invention;

FIG. 7 shows a block diagram that indicates an image forming systemincluding a multi function peripheral as an image forming apparatusaccording to Embodiment 2 of the present invention;

FIG. 8 shows a diagram that indicates an instance of service definitiondata described in WSDL;

FIG. 9 shows a diagram that indicates an instance of schema datareferenced in service definition data;

FIG. 10 shows a diagram that indicates an instance of a user interfacescreen;

FIG. 11 shows a diagram that indicates user interface data in which auser interface screen shown in FIG. 10 is described;

FIG. 12 shows a diagram that indicates a default screen displayed basedon a template file;

FIG. 13 shows a diagram that indicates a default screen displayed basedon a template file;

FIG. 14 shows a diagram that indicates a default screen displayed basedon a template file;

FIG. 15 shows a diagram that indicates a default screen displayed basedon a template file;

FIG. 16 shows a diagram that indicates a default screen displayed basedon a template file;

FIG. 17 shows a diagram that indicates an instance of a request messagein Embodiment 2 of the present invention;

FIG. 18 shows a diagram that indicates an instance of a response messagein Embodiment 2 of the present invention;

FIG. 19 shows a schematic flowchart that indicates process of a simpletext language processing program for a user application in the imageforming apparatus according to Embodiment 3 of the present invention;

FIG. 20 shows a diagram that indicates a part of data stored in PROM andDRAM in the image forming apparatus according to Embodiment 3 of thepresent invention;

FIG. 21A shows a diagram that indicates a main menu screen on anoperation panel of the image forming apparatus, FIG. 21B shows a diagramthat indicates a menu screen after the button “USER APPLICATION” ispushed down, and FIG. 21C shows a diagram that indicates a screen afterthe button 40 in FIG. 21B is pushed down;

FIG. 22 shows a diagram that indicates process of FIG. 19 along a graphof a remaining amount of toner in time series;

FIGS. 23A to 23C show diagrams that indicate specific instances of auser application for ordering a toner cartridge;

FIGS. 24A to 24C show diagrams that indicate specific instances of auser application for scanning a slip, facsimile transmission and emailtransmission;

FIG. 25 shows a schematic diagram that indicates a layer structure ofsoftware in the image forming apparatus of Embodiment 3; and

FIG. 26 shows a schematic diagram that indicates a hardwareconfiguration in the image forming apparatus of Embodiment 3.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Hereinafter, embodiments according to aspects of the present inventionwill be explained with reference to drawings.

Embodiment 1

FIG. 1 shows a block diagram that indicates an image forming systemincluding a multi function peripheral as an image forming apparatusaccording to Embodiment 1 of the present invention. In the system, amulti function peripheral 1 is connected to a computer network 2, and isused by either a terminal device 3 connected to the computer network 2or a user who operates an operation panel 11 of the multi functionperipheral 1. A user operation takes place to request to execute aservice, and then a request message and a response message aretransmitted either inside the multi function peripheral 1 or between themulti function peripheral 1 and the terminal device 3.

In FIG. 1, the multi function peripheral 1 has the operation panel 11, aprinting device 12, an image scanning device 13, a facsimile device 14,a data storage device 15, a communicating device 16 and a computer 17.

The operation panel 11 is a user interface device that contains (a) adisplay device such as liquid crystal display, and (b) an input devicethat detects a physical user operation electronically. The input devicemay be key switches, a transparent touch panel placed on a screen of thedisplay device, etc.

The printing device 12 is an internal device that prints a documentimage based on document data generated by the image scanning device 13,document data stored in a document box (not shown), document datareceived from the terminal device 3, or the like. The document data isimage data in a predetermined format.

The image scanning device 13 is an internal device that scans an imageof a document and outputs document data of the image. To scan the imageof the document fed by an auto document feeder or put by a user, theimage scanning device 13 radiates light to a single side or both sidesof the document, and detects reflection light or the like from thedocument.

The facsimile device 14 is an internal device that has a modem, andtransmits and receives facsimile signals. The facsimile device 14generates a facsimile signal from document data generated by the imagescanning device 13 or stored in the document box, and generates documentdata from a received facsimile signal.

The data storage device 15 is a device that stores service definitiondata 15 a, schema data 15 b, programs (not shown) to be executed by thecomputer 17, document data, etc. The data storage device 15 may be adevice that drives readable/writable recording medium such as hard diskdrive and/or non-volatile memory.

The service definition data 15 a is text data that contains (a) syntaxdefinitions of an interface part of a service, and (b) designation ofprotocol of messages to be used in the service. In the interface part,at least a call and a return value of the service are defined. Theservice definition data 15 a is described in XML, for example. Inaddition, the service definition data 15 a is described in WSDL, forexample. It should be noted that the service definition data 15 a isdata that contains syntax definitions, and is not transmitted as amessage. The service definition data 15 a can be stored as either onefile or a plurality of files. In the service definition data 15 a, aschema language is used to describe the syntax definitions. In thisembodiment, XML Schema is used to describe the syntax definitions in theservice definition data 15 a. The syntax definitions may be described inthe service definition data 15 a in XML Schema. Alternatively, areference to external schema data 15 b may be described in the servicedefinition data 15 a to read and use the schema data 15 b.

The schema data 15 b is external schema data referenced in the servicedefinition data 15 a. The schema data 15 b is text data described in apredetermined language. The schema data 15 b can be stored as either onefile or a plurality of files.

FIG. 2 shows a diagram that indicates an instance of the servicedefinition data 15 a described in WSDL. FIG. 3 shows a diagram thatindicates an instance of the schema data 15 b referenced in the servicedefinition data 15 a.

The service definition data 15 a shown in FIG. 2 contains syntaxdefinitions of an image scanning service with the image scanning device13. The service definition data 15 a shown in FIG. 2 consists of adefinition element of WSDL. A types element of WSDL is in the definitionelement, and an include element in the types element references theexternal schema data 15 b, for instance, “scan.xsd” shown in FIG. 3. Amessage element and a portType element of WSDL are in the definitionselement, and in the message element and the portType element, syntaxdefinitions of both a request message and a response message aredescribed as an interface part of the service. In FIG. 2, “send_request”is defined as a request message, and “send_response” is defined as aresponse message.

A binding element of WSDL is in the definitions element, and in thebinding element, a protocol of messages used for the service isdesignated. In the binding element shown in FIG. 2, SOAP is designatedas the protocol used for the messages.

In the schema data 15 b shown in FIG. 3, defined are (a) syntaxdefinitions of a request message and a response message, and (b)definitions of permissible values of parameters used in the messages.The syntax definitions of the messages are described as one or moreelement elements and one or more complexType elements of XML Schema(xsd), and a definition of the permissible values is described as asimpleType element of XML Schema (xsd).

As mentioned above, the service definition data 15 a has been stored inadvance for each of services. In addition, the external schema data 15 bhas been stored in advance if required.

The communicating device 16 is connected to the computer network 2, andis a device capable of communicating with another device (e.g. theterminal device 3) connected to the computer network 2. Thecommunicating device 16 may be a network interface card, or the like.

The computer 17 has a CPU (Central Processing Unit), a RAM (RandomAccess Memory), a ROM (Read Only Memory) and other components, and is adevice that loads a program to the RAM and executes the program with theCPU in order to realize processing units. The computer 17 realizes acommunication processing unit 21, an XML processing unit 22, a controlunit 23, and a driver 24 based on a program (not shown).

The communication processing unit 21 is a processing unit that controlsthe communicating device 16, and transmits/receives messages via thecomputer network 2 according to predetermined communication protocols.In this embodiment, since SOAP (Simple Object Access Protocol) is usedas a message protocol, TCP/IP (Transmission Control Protocol/InternetProtocol) and HTTP (Hypertext Transfer Protocol) are used ascommunication protocols.

The XML processing unit 22 reads out the service definition data 15 adescribed in WSDL (Web Services Description Language), and realizes amessage generating unit 22 a and a message parsing unit 22 b based onthe service definition data 15 a. The message generating unit 22 agenerates messages according to syntax definitions described in theservice definition data 15 a. The messages are a response message thatindicates a result of a service, a notification message, etc. Themessage parsing unit 22 b parses messages according to syntaxdefinitions described in the service definition data 15 a. The messagesare a request message that indicates a request of a service, etc. Themessage parsing unit 22 b identifies a request described in the messagebased on a result of parsing the message.

The control unit 23 is a processing unit that controls internal devicesto cause them to perform services according to a request identified bythe XML processing unit 22, and obtains results of the services from theinternal devices to provide the results to the XML processing unit 22.The internal devices such as the printing device 12, the image scanningdevice 13, and the facsimile device 14 have functions capable ofperforming the services.

The driver 24 is a driver of the operation panel 11, and is a processingunit that communicates with the XML processing unit 22 totransmit/receive messages in relation to information on a user operationinput to the operation panel 11 and information on a screen to bedisplayed on the operation panel 11.

In FIG. 1, the terminal device 3 has a communicating device 31, a datastorage device 32, and a computer 33. The terminal device 3 may be apersonal computer, or the like.

The communicating device 31 is connected to the computer network 2, andis a device capable of communicating with another device (e.g. the multifunction peripheral 1) connected to the computer network 2. Thecommunication device 31 may be a network interface card, or the like.

The data storage device 32 is a device that stores programs to beexecuted by the computer 33, etc. In the data storage device 32, adriver program 32 a has been stored. The data storage device 32 may be adevice that drives a readable/writable recording medium such as harddisk drive and/or non-volatile memory.

The computer 33 has a CPU, a RAM, a ROM and other components, and is adevice that loads a program to the RAM and executes the program with theCPU in order to realize processing units. The computer 32 realizes acommunication processing unit 41 and a driver 42 based on the driverprogram 33 a, etc.

The communication processing unit 41 is a processing unit that controlsthe communicating device 31, and transmits/receives messages via thecomputer network 2 according to predetermined communication protocols.In this embodiment, since SOAP messages are used as the messages, TCP/IPand HTTP are used as communication protocols.

The driver 42 is a driver that controls the multi function peripheral 1via the computer network 2, and is a processing unit thatgenerates/parses messages used for the services. Further, the driver 42obtains a part or all of both the service definition data 15 a and theschema data 15 b with controlling the communication processing unit 41,and identifies (a) a syntax of messages and (b) permissible values ofparameters used in the messages based on it.

Operations of the apparatus 1 and the device 3 are explained next.

In the multi function peripheral 1, after the computer is started,programs are executed by the computer 17, and consequently, thecommunication processing unit 21, the XML processing unit 22, thecontrol unit 23 and the driver 24 are realized. The XML processing unit22 reads out the service definition data 15 a after it is started, andconsequently, realizes the message generating unit 22 a and the messageparsing unit 22 b based on the service definition data 15 a. In thistime, the XML processing unit 22 also reads out the schema data 15 breferenced in the service definition data 15 a.

On the other hand, in the terminal device 3, the computer 33 executesthe driver program 32 a, etc., and consequently, the communicationprocessing unit 41 and the driver 42 are realized.

In the terminal device 3, if a predetermined user operation is detectedby an input device such as key board (not shown), then it is determinedthat a request of a service by a user takes place, and therefore, thedriver 42 executes a process to transmit a request message to the multifunction peripheral 1.

The driver 42 obtains a part or all of both the service definition data15 a and the schema data 15 b in relation to a service requested by auser. Specifically, the driver 42 transmits an HTTP command to apredetermined URL of the multi function peripheral 1 with controllingthe communication processing unit 41, and receives a part or all of theservice definition data 15 a and the schema data 15 b in a response fromthe multi function peripheral 1. For instance, the driver 42 may specifya URL of a data file that includes the service definition data 15 aand/or the schema data 15 b. Alternatively, the driver 42 may specify aURL of a CGI (Common Gate Interface) that distills and transmits arequested part in the data 15 a and 15 b as a response. Thecommunication processing unit 21 has an HTTP server function, andreceives the HTTP command and transmits a response to the terminaldevice 3.

The driver 42 identifies (a) a syntax of messages used in the serviceand (b) permissible values of parameters used in the service, from theobtained part or all of the service definition data 15 a and the schemadata 15 b. The driver 42 of the terminal device 3 identifies the name ofa message related to the service that a user requests, and identifiesthe syntax and the permissible values for messages that have the namefrom the service definition data 15 a and the schema data 15 b.

The driver 42 causes a display device (not shown) to display a list ofpermissible values of a parameter used in the service, and then selectsa value of the parameter from the list according to a user operationdetected by an input device (not shown), and generates a request messagethat contains the value.

For instance, in case that a request of an image scanning service takesplace, the driver 42 obtains a part or all of the service definitiondata 15 a and the schema data 15 b shown in FIGS. 2 and 3, and thendetermines that the parameter “file_format” (file_format element) andthe parameter “file_name” (file_name element) are used in the message“send_request”, and also determines that permissible values of theparameter “file_format” are “PDF”, “JPEG”, and “BMP”. The parameter“file_format” specifies a file format of a scanned image. In this case,the driver 42 causes a display device (not shown) to display (a) a listof the permissible values “PDF”, “JPEG”, and “BMP” of the parameter“file_format” and (b) a text to prompt a user to choose one of thevalues. For instance, if a user operation to choose “PDF” is detected,the driver 42 sets a value of the parameter “file_format” as “PDF”.Moreover, the driver 42 causes a display device (not shown) to displayan input field and a prompt text. The input field is to be input a valueof the parameter “file_name” that specifies a file name. The prompt textprompts a user to input the value to the input field. For instance, if auser operation to input the text “scan001” is detected, the driver 42sets a value of the parameter “file_name” as “scan001”. The driver 42generates a request message as shown in FIG. 4 with the selected valueof the parameter according to the obtained service definition data 15 aand the schema data 15 b. This generated message is a SOAP message. Itshould be noted that FIG. 4 indicates only a SOAP envelope part in theSOAP message.

As mentioned above, the terminal device 3 obtains the service definitiondata 15 a and the schema date 15 b from the multi function peripheral 1that performs a service, and therefore, it is not required that the data15 a and 15 b have been stored in the terminal device 3 in advance. Forinstance, even if different syntaxes are used for respective machinetypes of the multi function peripheral 1, it is not necessary that theservice definition data 15 a and the schema data 15 b have been storedfor the respective machine types, and the data 15 a and 15 b aremaintained only in the multi function peripheral 1.

The driver 42 causes the communication processing unit 41 to transmitthe generated request message to the multi function peripheral 1.Specifically, the communication processing unit 41 controls thecommunicating device 31, and causes the device 31 to transmit therequest message to the computer network 2 according to HTTP. Thetransmitted message is received by the communication processing unit 21of the multi function peripheral 1 through the communicating device 16from the computer network 2. The communication processing unit 21receives the message and transfers the message to the XML processingunit 22.

In the XML processing unit 22, the message parsing unit 22 b parses themessage according to the service definition data 15 a and the schemadata 15 b to identify a service that uses the message, and notifies thecontrol unit 23 of (a) a request by the message and (b) values ofparameters in the message. For instance, upon receiving the messageshown in FIG. 4, the message parsing unit 22 b determines that themessage is a send_request message of an image scanning service, andidentifies values of parameters specified in the message. The messageparsing unit 22 b notifies the control unit 23 of (a) the values of theparameters in the message and (b) receiving the send_request message ofan image scanning service.

Upon receiving the notification, the control unit 23 controls theinternal devices and causes the internal devices to perform therequested service. For instance, upon receiving the notification of (a)values of parameters specified in the message and (b) receiving asend_request message of an image scanning service, the control unit 23controls the image scanning device 13 and causes the image scanningdevice 13 to scan an image of a document. The image scanning device 13generates a file with a file name in a file format. The file includesdata of the scanned image, and the file name and the file format arespecified with the parameters.

Upon detecting that the internal device finishes performing the service,the control unit 23 notifies the message generating unit 22 a of aresult of the service.

The message generating unit 22 a receives the notification of the resultof the service, and then generates a response message according to theservice definition data 15 a and the schema data 15 b.

For instance, the message generating unit 22 a receives, as anotification of the result of the image scanning service, a transmissionrequest of a send_response message (i.e. a response message) of theimage scanning service defined in the service definition data 15 a shownFIG. 2. Upon receiving it, the message generating unit 22 a identifiessyntax of the response with the service definition data 15 a and theschema data 15 b shown in FIGS. 2 and 3, and also identifies permissiblevalues of the parameter “result” (result element) in the message. Basedon the service definition data 15 a and the schema data 15 b shown inFIGS. 2 and 3, it is determined that (a) a result element exists in thesend_response message, (b) permissible values of the result element are“SUCCESS”, “JOB_CANCELED_ERROR”, and “INTERNAL_ERROR”, etc. The messagegenerating unit 22 a selects a value of the result element from“SUCCESS”, “JOB_CANCELED_ERROR”, and “INTERNAL_ERROR” corresponding tothe notification from the control unit 23, and generates a SOAP messagethat contains the result element with the value. For instance, in casethat the control unit 23 notifies the message generating unit 22 a offinishing the requested image scanning service successfully, the messagegenerating unit 22 a generates a SOAP message as shown in FIG. 5. Itshould be noted that FIG. 5 indicates only a SOAP envelope part in theSOAP message.

The XML processing unit 22 causes the communication processing unit 21to transmit the generated response message to the terminal device 3. Thecommunication processing unit 21 controls the communicating device 16,and causes the device 16 to transmit the message to the computer network2 according to HTTP. The transmitted message is received by thecommunication processing unit 41 of the terminal device 3 through thecommunicating device 31 from the computer network 2. The communicationprocessing unit 41 receives the message and transfers the message to thedriver 42. The driver 42 detects the result of the requested service inthe response message. The driver 42 executes a process corresponding tothe result. For instance, the driver 42 causes a display device (notshown) to display the result of the service. Further, for instance, incase of an image scanning service, in the multi function peripheral 1,an image data file that has been encoded to text data may be insertedinto the response message, and the driver 42 may obtain the originalimage data file with decoding the text data in the message.

As mentioned above, a request and a response are transmitted andreceived in relation to a service. In case that a request of a servicetakes place due to a user operation to the operation panel 11, as wellas the driver 42, the driver 24 can communicate with the XML processingunit 22 to transmit/receive a request message and a response message, sothat executed is the process as same as the aforementioned one.

FIG. 6 shows a diagram that indicates a layer structure of messagecommunication process in Embodiment 1 of the present invention. As shownin FIG. 6, in this system, (a) a program interface part of messagetransmission and message receipt, and (b) an implementation part ofmessage communication are defined separately. Even if the implementationpart (i.e. a part defined in the aforementioned binding element) ischanged, it is not necessary to change the program interface part (i.e.a part defined in the aforementioned message element), the drivers 24,42, and the control unit 23 used to perform a service. Further, onlyediting text data i.e. the service definition data 15 a and/or theschema data 15 b can change the implementation part of messagecommunication. Therefore, significant changes in the apparatus 1 and thedevice 3 are not required to change a specification of messages used forservices.

Embodiment 2

FIG. 7 shows a block diagram that indicates an image forming systemincluding a multi function peripheral as an image forming apparatusaccording to Embodiment 2 of the present invention. In the system, amulti function peripheral 101 is connected to a computer network 102,and is used by either a terminal device 103 connected to the computernetwork 102 or a user who operates an operation panel 111 of the multifunction peripheral 101. A user operation takes place to request toperform a service, and then a request message and a response message aretransmitted either inside the multi function peripheral 101 or betweenthe multi function peripheral 101 and the terminal device 103.

In FIG. 7, the multi function peripheral 101 has the operation panel111, a printing device 112, an image scanning device 113, a facsimiledevice 114, a data storage device 115, a communicating device 116, and acomputer 117.

The operation panel 111 is a user interface device that contains (a) adisplay device 111 a such as liquid crystal display, and (b) an inputdevice 111 b that detects a physical user operation electronically. Theinput device 111 b may be key switches, a transparent touch panel placedon a screen of the display device, etc.

The printing device 112 is an internal device that prints a documentimage based on document data generated by the image scanning device 113,document data stored in a document box (not shown), document datareceived from the terminal device 103, or the like. The document data isimage data in a predetermined format.

The image scanning device 113 is an internal device that scans an imageof a document and outputs document data of the image. To scan the imageof the document fed by an auto document feeder or put by a user, theimage scanning device 113 radiates light to a single side or both sidesof the document, and detects reflection light or the like from thedocument.

The facsimile device 114 is an internal device that has a modem, andtransmits and receives facsimile signals. The facsimile device 114generates a facsimile signal from document data generated by the imagescanning device 113 or stored in the document box, and generatesdocument data from a received facsimile signal.

The data storage device 115 is a device that stores service definitiondata 115 a, schema data 115 b, user interface data 115 c, template files115 d, programs (not shown) to be executed by the computer 117, documentdata, etc. The data storage device 115 may be a device that drivesreadable/writable recording medium such as hard disk drive and/ornon-volatile memory.

The service definition data 115 a is text data that contains (a) syntaxdefinitions of an interface part of a service, and (b) designation ofprotocol of messages to be used in the service. In the interface part,at least a call and a return value of the service are defined. Theservice definition data 115 a is described in XML, for example. Inaddition, the service definition data 115 a is described in WSDL, forexample. It should be noted that the service definition data 115 a isdata that contains syntax definitions, and is not transmitted as amessage. The service definition data 115 a can be stored as either onefile or a plurality of files. In the service definition data 115 a, aschema language is used to describe the syntax definitions. In thisembodiment, XML Schema is used to describe the syntax definitions in theservice definition data 115 a. The syntax definitions may be describedin the service definition data 115 a in XML Schema. Alternatively, areference to external schema data 115 b may be described in the servicedefinition data 115 a to read and use the schema data 115 b.

The schema data 115 b is external schema data referenced in the servicedefinition data 115 a. The schema data 115 b is text data described in apredetermined language. The schema data 115 b can be stored as eitherone file or a plurality of files.

FIG. 8 shows a diagram that indicates an instance of the servicedefinition data 115 a described in WSDL. FIG. 9 shows a diagram thatindicates an instance of the schema data 115 b referenced in the servicedefinition data 15 a.

The service definition data 115 a shown in FIG. 8 contains syntaxdefinitions of an editing service for the user interface data 115 c. Inthe editing service, it is possible to change, add or delete a componentof a user interface screen in the user interface data 115 c. The servicedefinition data 115 a shown in FIG. 8 consists of a definition elementof WSDL. A types element of WSDL is in the definition element, and aninclude element in the types element references the external schema data115 b, for instance, “panel.xsd” shown in FIG. 9. A message element anda portType element of WSDL are in the definitions element, and in themessage element and the portType element, syntax definitions of both arequest message and a response message are described as an interfacepart of the service. In the portType element, operation elements aredescribed. The operation element indicates respective operations thatcan be requested to the multi function peripheral 101. As shown FIG. 8,an operation element to add a button to a user interface screen isdescribed, and in the operation element, “button_request” is defined asa request message, and “button_response” is defined as a responsemessage. Also described are an operation element to delete a button in auser interface screen, an operation element to update attributioninformation on a button in a user interface screen, etc. Moreover, anoperation element is contained for adding, deleting and updating anothercomponent (e.g. list box, text box, etc.) in a user interface screen.

A binding element of WSDL is in the definitions element, and in thebinding element, a protocol of messages used for the service isdesignated. In the binding element shown in FIG. 8, SOAP is designatedas the protocol used for the messages.

In the schema data 115 b shown in FIG. 9, described are (a) syntaxdefinitions of a request message (button_request), (b) syntaxdefinitions (not shown) of a response message, and (c) definitions (notshown) of permissible values of parameters used in the messages. Thesyntax definitions of the messages are described as one or more elementelements and one or more complexType elements of XML Schema (xsd). Adefinition of the permissible values is described as a simpleTypeelement of XML Schema (xsd). In this embodiment, the schema data 115 balso contains syntax definitions of describing attribution informationon components of a user interface screen in the user interface data 115c. These syntax definitions are also used to describe the attributioninformation on components of a user interface screen in a message. Thesyntax definitions include (a) attribution items of the componentsand/or (b) available setting values (i.e. permissible values) of theattribution items.

As mentioned above, the service definition data 115 a has been stored inadvance for each of services. In addition, the external schema data 115b has been stored in advance if required.

The user interface data 115 c is text data that contains attributioninformation on components in a user interface screen displayed by thedisplay device 111 a of the operation panel 111. In case that userinterface screens are used, different pieces of attribution informationare described on components in the respective user interface screens.The user interface data 115 c is described in XML according to thesyntax definitions in the schema data 115 b. FIG. 10 shows a diagramthat indicates an instance of a user interface screen. The userinterface screen shown in FIG. 10 contains the components: “SETTING”text, “COPY” button, “FACSIMILE” button, and “PRINTER” button. FIG. 11shows a diagram that indicates the user interface data 115 c in which auser interface screen shown in FIG. 10 is described. As shown in FIG.11, a user interface screen is described as a screen element, and thescreen element has child elements: (a) a screen_name element thatcontains the name of the user interface screen, (b) a screen_titleelement that contains attribution information on the “SETTING” text, and(c) three button elements that contain pieces of attribution informationon the “COPY” button, the “FACSIMILE” button, and the “PRINTER” button.The button element has child elements: (a) an event_button element thatcontains attribution information on displaying the button, and (b) aprocedure_string element that specifies an action to be performed whenthe button is operated. The event_button element contains (a) abutton_name element that contains identification information (a buttonname), (b) a button_string element that contains a button name to bedisplayed, (c) a button_top element that contains a coordinate value ofthe top of a button in vertical direction, (d) a button_left elementthat contains a coordinate value of the left edge of a button inhorizontal direction, (e) a button_height element that contains a valueof button height, and (f) a button_width element that contains a valueof button width.

The template files 115 d are default data in which components of userinterface screens are described in XML. The template files 115 d arealso described according to the syntax definition in the schema data 115b. Each of the template files 115 d contains attribution information onone or more components in one of the user interface screen together withone or more default values of the attribution. It is possible to use anXML text in the template files 115 d for customizing the user interfacedata 115 c. FIGS. 12 to 16 show diagrams that indicate default screensdisplayed based on the template files 115 d. FIG. 12 shows abutton-selection-type screen that contains the components of one or morebuttons and one or more texts. FIG. 13 shows a list-type screen thatcontains a list of the components. FIG. 14 shows a numerical-input-typescreen that contains an input field as the component. FIG. 15 shows atext-input-type screen that contains a text input field as thecomponent. FIG. 16 shows a number-selecting-type screen that contains anumeric increment button, a numeric decrement button and a numericalvalue field as the components.

The communicating device 116 is connected to the computer network 102,and is a device capable of communicating with another device (e.g. theterminal device 103) connected to the computer network 102. Thecommunicating device 116 may be a network interface card, or the like.

The computer 117 has a CPU (Central Processing Unit), a RAM (RandomAccess Memory), a ROM (Read Only Memory) and other components, and is adevice that loads a program to the RAM and executes the program with theCPU in order to realize processing units. The computer 117 realizes acommunication processing unit 121, an XML processing unit 122, a controlunit 123, and a driver 124 based on a program (not shown).

The communication processing unit 121 is a processing unit that controlsthe communicating device 116, and transmits/receives messages via thecomputer network 102 according to predetermined communication protocols.In this embodiment, since SOAP (Simple Object Access Protocol) is usedas a message protocol, TCP/IP (Transmission Control Protocol/InternetProtocol) and HTTP (Hypertext Transfer Protocol) are used ascommunication protocols.

The XML processing unit 122 reads out the service definition data 115 adescribed in WSDL and realizes a message generating unit 122 a and amessage parsing unit 122 b based on the service definition data 115 a.The message generating unit 122 a generates messages according to syntaxdefinitions described in the service definition data 115 a. The messagesare a response message that indicates a result of a service, anotification message, etc. The message parsing unit 122 b parsesmessages according to syntax definitions described in the servicedefinition data 115 a. The messages are a request message that indicatesa request of a service, etc. The message parsing unit 122 b identifies arequest described in the message based on a result of parsing themessage. The UI data parsing unit 122 c identifies attributions of thecomponents with parsing the user interface data 115 c, and causes thedisplay device 111 a to display the user interface screen that reflectsthe attributions of the components. The UI data parsing unit 122 ccauses the driver 124 to display the user interface screen based on aresult of parsing the data 115 c.

The control unit 123 is a processing unit that controls internal devicesto cause them to perform services according to a request identified bythe XML processing unit 122, and obtains results of the services fromthe internal devices to provide the results to the XML processing unit122. The internal devices such as the printing device 112, the imagescanning device 113, and the facsimile device 114 have functions capableof performing the services.

The driver 124 is a driver of the operation panel 111, and is aprocessing unit that communicates with the XML processing unit 122 totransmit/receive messages in relation to information on a user operationinput to the operation panel 111 and information on a user interfacescreen to be displayed on the operation panel 111.

In FIG. 7, the terminal device 103 has a communicating device 131, adata storage device 132, and a computer 133. The terminal device 103 maybe a personal computer, or the like.

The communicating device 131 is connected to the computer network 102,and is a device capable of communicating with another device (e.g. themulti function peripheral 101) connected to the computer network 102.The communication device 131 may be a network interface card, or thelike.

The data storage device 132 is a device that stores programs to beexecuted by the computer 133, etc. In the data storage device 132, adriver program 132 a has been stored. The data storage device 132 may bea device that drives a readable/writable recording medium such as harddisk drive and/or non-volatile memory.

The computer 133 has a CPU, a RAM, a ROM and other components, and is adevice that loads a program to the RAM and executes the program with theCPU in order to realize processing units. The computer 132 realizes acommunication processing unit 141 and a driver 142 based on the driverprogram 133 a, etc.

The communication processing unit 141 is a processing unit that controlsthe communicating device 131, and transmits/receives messages via thecomputer network 102 according to predetermined communication protocols.In this embodiment, since SOAP messages are used as the messages, TCP/IPand HTTP are used as communication protocols. For instance, thecommunication processing unit 141 transmits a request message to editthe user interface data 115 c.

The driver 142 is a driver that controls the multi function peripheral101 via the computer network 102, and is a processing unit thatgenerates/parses messages used for the services. Further, the driver 142obtains a part or all of both the service definition data 115 a and theschema data 115 b with controlling the communication processing unit141, and identifies (a) a syntax of messages, (b) attribution items usedin the messages, and (c) permissible values to be set to the attributionitems.

Displaying a user interface screen in the multi function peripheral 101is explained next.

In the multi function peripheral 101, after the computer 117 is started,programs are executed by the computer 117, and consequently, thecommunication processing unit 121, the XML processing unit 122, thecontrol unit 123 and the driver 124 are realized.

After the computer 117 is started, the UI data parsing unit 122 c readsout an XML text of a predetermined initial screen from the userinterface data 115 c, parses the XML text, and provides an instructionto the driver 124 according to a result of parsing the XML text. Thedriver causes the display unit 111 a to display the initial screenaccording to the instruction.

If the input device 111 b detects a user operation while the initialscreen is displayed, then information on the user operation is suppliedto the XML processing unit 122 through the driver 124. The UI dataparsing unit 122 c takes the user operation into account, and if the UIdata parsing unit 122 c determines that a screen transition isnecessary, the UI data parsing unit 122 c reads out an XML text of anext screen from the user interface data 115 c, parses the XML text, andprovides an instruction to the driver 124 according to a result ofparsing the XML text. The driver 124 makes a screen transition andcauses the display unit 111 a to display the next screen according tothe instruction.

Afterward, a screen transition is also made every time when it becomesnecessary due to a user operation or a state transition of the multifunction peripheral 101.

In the following part, customizing a user interface screen in the multifunction peripheral 101 is explained. A user or a serviceperson operatesthe terminal device 103 for the customization.

The XML processing unit 122 reads out the service definition data 115 aafter it is started, and consequently, realizes the message generatingunit 122 a and the message parsing unit 122 b based on the servicedefinition data 115 a. In this time, the XML processing unit 122 alsoreads out the schema data 115 b referenced in the service definitiondata 115 a.

On the other hand, in the terminal device 103, the computer 133 executesthe driver program 132 a, etc., and consequently, the communicationprocessing unit 141 and the driver 142 are realized.

In the terminal device 103, if a predetermined user operation isdetected by an input device such as key board (not shown), then it isdetermined that a request of a service by a user takes place, andtherefore, the driver 142 executes a process to transmit a requestmessage to the multi function peripheral 101.

The driver 142 obtains a part or all of the service definition data 115a and the schema data 115 b in relation to a service requested by auser. Specifically, the driver 142 transmits an HTTP command to apredetermined URL of the multi function peripheral 101 with controllingthe communication processing unit 141, and receives a part or all of theservice definition data 115 a and the schema data 115 b in a responsefrom the multi function peripheral 101. For instance, the driver 142 mayspecify a URL of a data file that includes the service definition data115 a and/or the schema data 115 b. Alternatively, the driver 142 mayspecify a URL of a CGI (Common Gate Interface) that distills andtransmits a requested part in the data 115 a and 115 b as a response.The communication processing unit 121 has an HTTP server function, andreceives the HTTP command and transmits a response to the terminaldevice 103.

The driver 142 identifies (a) a syntax of messages used in the serviceand (b) permissible values of parameters used in the service, from theobtained part or all of the service definition data 115 a and the schemadata 115 b. The driver 142 of the terminal device 103 identifies thename of a message related to the service that a user requests, andidentifies the syntax and the permissible values for messages with thename from the service definition data 115 a and the schema data 115 b.

The driver 142 causes a display device (not shown) to display a list ofpermissible values of a parameter used in the service, and then selectsa value of the parameter from the list according to a user operationdetected by an input device (not shown), and generates a request messagethat contains the value.

For instance, in case that a request of a user interface screen editingservice to add a button takes place, the driver 142 obtains a part orall of the service definition data 115 a and the schema data 115 b shownin FIGS. 8 and 9, and identifies parameters and attribution items withthe obtained data. The driver 142 determines that the parameters“screen_name” (screen_name element), “event_button” (event_buttonelement) and “procedure_string” (procedure_string element) are used in a“send_request” message, and also determines that the attribution itemsin the parameter “event_button” are “button_name”, “button_string”,“button_top”, “button_left”, “button_height”, and “button_width”. Thedriver 142 causes a display device (not shown) to display a screen thatprompts the user or the serviceperson to input values of the parametersand the attribution items. If text input of the parameters and theattribution items is detected by an input device (not shown), the driver142 generates a request message as shown in FIG. 17 with the selectedvalue of the parameter according to the obtained service definition data115 a and the schema data 115 b. This generated message is a SOAPmessage. It should be noted that FIG. 17 indicates only a SOAP envelopepart in the SOAP message.

As mentioned above, the terminal device 103 obtains the servicedefinition data 115 a and the schema data 115 b from the multi functionperipheral 101 that performs a service, and therefore, it is notrequired that the data 115 a and 115 b have been stored in the terminaldevice 103 in advance. For instance, even if different syntaxes are usedfor respective machine types of the multi function peripheral 101, it isnot necessary that the service definition data 115 a and the schema data115 b have been stored for the respective machine types, and the data115 a and 115 b are maintained only in the multi function peripheral101.

The driver 142 causes the communication processing unit 141 to transmitthe generated request message to the multi function peripheral 101.Specifically, the communication processing unit 141 controls thecommunicating device 131, and causes the device 131 to transmit therequest message to the computer network 102 according to HTTP. Thetransmitted message is received by the communication processing unit 121of the multi function peripheral 101 through the communicating device116 from the computer network 102. The communication processing unit 121receives the message and provides the message to the XML processing unit122.

In the XML processing unit 122, the message parsing unit 122 b parsesthe message according to the service definition data 115 a and theschema data 115 b to identify a service that uses the message, andnotifies the control unit of (a) a request by the message and (b) valuesof parameters in the message. For instance, upon receiving the messageshown in FIG. 17, the message parsing unit 122 b determines that themessage is a send_request message of a user interface screen editingservice, and identifies values of parameters specified in the message.The message parsing unit 122 b notifies the control unit 123 of (a) thevalues of the parameters in the message and (b) receiving thesend_request message of a user interface screen editing service.

Upon receiving the notification, the control unit 123 controls theinternal devices and causes the internal devices to perform therequested service. For instance, upon receiving the notification of (a)values of parameters specified in the message and (b) receiving asend_request message of a user interface screen editing service, thecontrol unit 123 edits the user interface data 115 c stored in the datastorage device 115. Specifically, in case of adding or updating acomponent, the control unit 123 writes the component (i.e. XML element)described in the received request message into the user interface data115 c without any modifications of the XML element. For instance, anevent_button element and a procedure_string element described in FIG. 17are added to the user interface data 115 c without any editing and anyconversion of the elements.

If the control unit 123 finishes performing the service, the controlunit 123 notifies the message generating unit 122 a of a result of theservice.

The message generating unit 122 a receives the notification of theresult of the service, and then generates a response message accordingto the service definition data 115 a and the schema data 115 b.

For instance, the message generating unit 122 a receives, as anotification of the result of the user interface screen editing service,a transmission request of a send_response message (i.e. a responsemessage) of the service in the service definition data 115 a. Uponreceiving it, the message generating unit 122 a identifies syntax of theresponse SOAP message from the service definition data 115 a and theschema data 115 b, and generates the response SOAP message. Forinstance, in case that the control unit notifies the message generatingunit 122 a of finishing the requested user interface screen editingservice successfully, the message generating unit 122 a generates a SOAPmessage as shown in FIG. 18. It should be noted that FIG. 18 indicatesonly a SOAP envelope part in the SOAP message.

The XML processing unit 122 causes the communication processing unit 121to transmit the generated response message to the terminal device 103.The communication processing unit 121 controls the communicating device116, and causes the device 116 to transmit the message to the computernetwork 102 according to HTTP. The transmitted message is received bythe communication processing unit 141 of the terminal device 103 throughthe communicating device from the computer network 102. Thecommunication processing unit 141 receives the message and provides themessage to the driver 142. The driver 142 detects the result of therequested service in the response message. The driver 142 executes aprocess corresponding to the result. For instance, the driver 142 causesa display device (not shown) to display the result of the service.Further, for instance, in case of the user interface screen editingservice, in the multi function peripheral 101, the user interface data115 c of the edited user interface screen may be inserted into theresponse message, and the driver 142 of the terminal device 103 causesto display the edited user interface screen based on the user interfacedata 115 c in the message.

Further, in the user interface screen editing service, a user interfacescreen may be added or updated with the template files 115 d. In thiscase, for instance, the terminal device 103 transmits a request messageto the multi function peripheral 101. The request message specifies auser interface screen and one of the template files 115 d. In the multifunction peripheral 101, the user interface data 115 of the specifieduser interface screen is updated with the specified template file, ordata in the specified template file is added to the user interface data115 as data of the specified user interface screen. Syntax definitionsof this request message are also in the service definition data 115 aand the schema data 115 b. Afterward, it is possible to edit componentsin the user interface screen that generated from the template file.

As mentioned above, according to Embodiment 2, the multi functionperipheral 101 contains the display device 111 a that displays a userinterface screen; the data storage device 115 that stores the userinterface data 115 c containing attributions of components in the userinterface screen; and the UI data parsing unit 122 c that identifiesattributions of the components with parsing the user interface data, andcauses the display device 111 a to display the user interface screenthat reflects the attributions of the components. The user interfacedata is described as text data.

Therefore, it is possible to customize a user interface by editing userinterface data 115 c in a text format. Consequently, it is possible tocustomize a user interface screen of the multi function peripheral 101easily.

Further, according to Embodiment 2, the multi function peripheral 101contains: the XML processing unit 122 that parses a message according tothe service definition data 115 a; and the control unit 123 thatexecutes the editing service according to a request obtained from aresult of parsing the message by the XML processing unit 122. Theservice definition data 115 a includes syntax definitions of aninterface part of an editing service of the user interface data 115 cand designation of a protocol to be used for the service.

Therefore, the multi function peripheral 101 performs editing the userinterface data 115 c as a service, and consequently, it is possible toedit the user interface data 115 c by transmitting a message from anexternal device to the multi function peripheral 101 without operatingthe multi function peripheral 101 directly. Consequently, it is possibleto customize a user interface screen of the multi function peripheral101 easily.

Further, according to Embodiment 2, in the multi function peripheral101, the user interface data 115 c and the message are described in XML,and the control unit 123 updates the user interface data 115 c with anXML text of the attributions of the components distilled by the messageprocessing unit 122 b.

Therefore, conversion from a message to an XML text for the userinterface data 115 c is not necessary when the user interface data 115 cis updated.

Further, according to Embodiment 2, in the terminal device 103, thedriver 142 obtains a part or all of the schema data 115 b from the multifunction peripheral 101 and identifies one or more items in theattributions of the components with the part or all of the schema data115 b.

Therefore, it is possible to customize the image forming apparatuswithout storing items of the components in the terminal device 103 inadvance.

Further, according to Embodiment 2, in the terminal device 103, thedriver 142 obtains a part or all of the schema data 115 b from the multifunction peripheral 101 and identifies one or more permissible values onthe attributions of the components with the part or all of the schemadata 115 b. The communication processing unit 141 transmits the messageto set a value selected from the one or more permissible values to oneof the attributions.

Therefore, it is possible to customize the image forming apparatuswithout storing items of the components in the terminal device 103 inadvance.

Further, according to Embodiment 2, the user interface data 115 c andthe message are described in XML, the schema data 115 b is XML datadescribed in XML Schema, and the control unit 123 updates the userinterface data 115 c with an XML text of the attributions of thecomponents distilled by the XML processing unit 122.

Therefore, it is possible to customize the image forming apparatuswithout storing syntax definitions in the terminal device 103 inadvance.

Further, according to Embodiment 2, the data storage device 115 storesthe template files 115 d containing respective default data of the userinterface screen. The communication processing unit 141 of the terminaldevice 103 selects one of the template files 115 d and transmits themessage to set default data in the selected template file as data of oneof user interface screens in the user interface data 115 c.

Therefore, it is possible to execute complex customization easily withusing the templates.

Embodiment 3

As well as Embodiment 2, in Embodiment 3, buttons are displayed in anoperation panel of an image forming apparatus, and attributioninformation on the buttons is described in a text format. In terms of asimple text language processing program, the attribution information ina text format is parsed, the buttons are displayed according to theattribution information, and a process specified by the attributioninformation is executed when the buttons are operated.

FIG. 26 shows a schematic diagram that indicates a hardwareconfiguration in the image forming apparatus 210 of Embodiment 3.

In the image forming apparatus 210, an MPU 211 is connected viainterfaces 212 to a PROM 213, a DRAM 214, an operation panel 215, aprinter 216, a scanner 217, a NIC 218, a FAX modem 219, a USB port 220,a toner remaining amount detector 221, an IC card reader 222, anelectronic tag reader 223, and a timer TM. In FIG. 26, for simplicity,the interfaces are depicted as one block.

The PROM 213 is, for example, a flash memory. In the PROM 213, anoperating system (OS), programs to be executed in an upper layer of theOS, and setting values have been stored. The programs realize functionsof a multi function peripheral in the image forming apparatus 210. Thefunctions include copying, scanning, printing, facsimiletransmission/reception, email transmission/reception, and HTTPcommunication. The DRAM 214 is a memory for a work area.

The operation panel 215 has a display unit and a key input unit, detectsinput of setting information or instruction, and displays a screen suchas selection screen or setting screen. The printer 216 has a printengine, a fuser, a paper feeding part, a paper transporting part, and apaper outputting part. The printer 216 forms an electrostatic latentimage on a photoconductor drum in the print engine with bitmap datasupplied as print data, develops it with toner, transfers the tonerimage onto a sheet, fixes the toner image, and outputs the sheet. Thescanner 217 is a device to input an image for copying and facsimiletransmission. The network interface card (NIC) 218 is connected to ahost computer and a server on a network, and is used for a print job andordering consumable goods. The FAX modem 219 is a communicating devicefor facsimile transmission/reception.

The toner remaining amount detector 221 detects a remaining amount oftoner in a toner cartridge for the printer 216, and outputs a signalthat indicates the remaining amount of toner. The IC card reader 222wirelessly communicates with an IC card placed within a communicablearea to transmit/receive signals, reads out a user ID and a passwordfrom the IC card, and outputs them to the image forming apparatus 210 asauthentication information. The electronic tag reader 223 reads out atoner cartridge ID from an electronic tag fixed in the toner cartridge,and outputs the ID. This ID contains the type and the serial number ofthe toner cartridge.

Outputs of the toner remaining amount detector 221 and the electronictag reader 223 are detected by the MPU 211 according to a program bothperiodically and when the toner cartridge is mounted. The outputs arestored in the DRAM 214 as Toner.Level and Toner.RFID.

A USB memory 224A connected to the port 220 has, for example, a flashmemory chip.

A NIC of the host computer 225 is connected to the NIC 218 via a hub,and to the Internet 226 via a router (not shown). A web server machine227 is connected to the Internet 226 via a router (not shown). A FAXmodem of the web server machine 227 is connected to the FAX modem 219 ofthe image forming apparatus 210 via a public switched telephone network228.

The timer TM is used for detecting current time and for timerinterruptions to the MPU 211.

FIG. 25 shows a schematic diagram that indicates a layer structure ofsoftware in the image forming apparatus of Embodiment 3.

An OS 230 contains a kernel (e.g. Linux), device drivers 231 ofrespective pieces of hardware.

A fundamental service program 233 is in an upper layer than the OS 230.The fundamental service program 233 is middleware that uses functions ofthe OS 230 through an API 232. The fundamental service program 233 hasan operation panel control module 330, a scan module 331 as an imageinput module, a data processing module that processes input data, aprint module 332 as an image output module that outputs processed imagedata, and an input/output module.

The operation panel control module 330 causes the operation panel 215 todisplay buttons to be pushed down. The input/output module contains aFAX transmission/reception module 333, an email transmission/receptionmodule 334, and an HTTP processing module 339. The data processingmodule contains an IC card control module 335, an RFID control module336, a format conversion module 337, an aggregate processing module (notshown), a page numbering module (not shown), etc. The format conversionmodule 337 converts a format of image data. The fundamental serviceprogram 233 further contains an address book module 338 as a utilitymodule. The address book module 338 is used to specify addresses offacsimile and email.

An external API 234 and an application 235 are in an upper layer thanthe fundamental service program 233. The application 235 is a programcapable of using modules in the fundamental service program 233 throughthe external API 234. The application 235 contains a copy module 350, aprint module 351, a FAX module 352, an email module 353, a jobmanagement module 354, and an operation panel module 355. For example,the copy module 350 is composed from the combination of the scan module331 and the print module 332. For example, the FAX module 352 iscomposed from the combination of the FAX transmission/reception module333 and the address book module 338.

Software of the image forming apparatus 210 contains a simple textlanguage processing program 238. The simple text language processingprogram 238 is an interpreter for a user application 237. The languageprocessing program 238 interprets a statement to the user application237, and causes the user application 237 to run with calling a functionin the fundamental service program 233, the application 235 or the OS230 through the external API 234, the external API 236 or the API 232.

The user application 237 is generated through a grammatical check andcopied into the USB memory 224A, for example, in the host computer 225,and is read from the USB memory 224A to the DRAM 214 via the port 220.Line numbers are attached to respective lines in the user application237 in a preprocess. FIGS. 23A to 23C indicate specific instances of theuser application 237.

On the operation panel 215, a main menu screen is displayed as shown inFIG. 21A. If a user touches (i.e. pushes down) “USER APPLICATION” buttonin the screen, a process is started along a flowchart shown in FIG. 19.The process displays components other than the text “USER APPLICATION”in FIG. 21B.

FIG. 19 shows a schematic flowchart that indicates a process of thesimple text language processing program 238 for the user application237.

This process is started repeatedly, for instance, every 20 milliseconds,by a timer interruption. This process shown in FIG. 19 is explainednext.

-   (Step S0) set the initial value of a counter LC as zero. The counter    LC indicates a line number of a line to be processed next in the    user application 237.-   (Step S1) read out the line specified by the counter LC from the    user application 237, set a current line counter CLC as the value of    the counter LC, and then set the counter LC as the line number of a    statement next to the statement in the line specified by the counter    CLC. A delimiter of the statement is either a semicolon or a close    brace as well as ones in C language. In the case shown in FIG. 23A,    the LC changes from LC=0 to LC=1, and changes LC=1 to LC=7 if the    condition in Line 1 is not satisfied, or changes LC=1 to LC=2 if the    condition in Line 1 is satisfied at Step S10 mentioned below.-   (Step S2) end this process if the line to be read out does not    exist, otherwise go to Step S3.-   (Step S3) go to Step S4 if the statement is a ResetEnd statement,    otherwise go to Step S7.-   (Step S4) return to Step S1 if the value of an end flag EF is “0”,    or go to Step S5 if the value of the end flag EF is “1”.-   (Step S5) determine whether or not a condition expression (REC)    between braces in the ResetEnd statement is satisfied; go to Step S6    if the condition expression is satisfied, otherwise end this process    shown in FIG. 19.-   (Step S6) reset the end flag EF to “0”, clear the order-completed    indication mentioned below on the operation panel 215, and return to    Step S1.-   (Step S7) go to Step S8 if the line specified by the CLC contains a    condition phrase, otherwise go to Step S11.

In the case shown in FIG. 23A, “If Toner.Level<Level.Low1 {” in the lineof LC=1 and “Button(120, 80, 60, 30, CARTRIDGE ORDER & CrLf & REMAIN &Toner.Level.ToPages & SHEETS) {” in the line of LC=2 are conditionphrases.

The latter has been simplified from the condition phrase (with theButton phrase) “If Button(120, 80, 60, 30, CARTRIDGE ORDER & CrLf &REMAIN & Toner.Level.ToPages & SHEETS) is pushed {”. Due to thissimplification, a nest structure in condition statements is hidden, andconsequently, the user application 237 is clear and easy to write.

-   (Step S8) if the line specified by the CLC contains a Button phrase,    generate data to display a button based on arguments of the Button    phrase, and cause the operation panel 215 to display the button    based on the data, for example, a button 240 shown in FIG. 21B.

The Button phrase of LC=2 contains the arguments “120, 80, 60, 30,CARTRIDGE ORDER & CrLf & REMAIN & Toner.Level.ToPages & SHEETS”. Thearguments “120, 80” mean X-Y coordinates of the top left corner of thebutton in the operation panel 215. The arguments “60, 30” mean the widthand the height of the button. The argument “CARTRIDGE ORDER & CrLf &REMAIN & Toner.Level.ToPages & SHEETS” means the text to be indicated onthe button. In the text, “&” is a concatenation operator of texts,“CrLf” is a control code for carriage return, “Toner.Level.ToPages”means the estimated number of available printing sheets derived from thedetected remaining amount of toner mentioned above. Generating data todisplay the button and displaying the button are performed withfunctions in the operation panel control module 330 and the operationpanel module 355.

Right after the button is displayed, an internal flag F is set, andafterward, if in Step S8 it is determined that the flag F has been set,generating the data of the button is omitted.

-   (Step S9) determine whether or not a condition expression in the    condition phrase is satisfied, go to Step S10 if it is determined    that it is satisfied, otherwise return to Step S1.-   (Step S10) update the value of the counter LC with the value CLC+1    if the condition expression is satisfied, and return to Step S1.-   (Step S11) go to Step S13 if the line specified by the line counter    CLC is an End statement, otherwise go to Step S12.-   (Step S12) process the line specified by the counter CLC, and then    return to Step S1.-   (Step S13) execute the End statement, and then end the process shown    in FIG. 19. Specifically, the button displayed on the operation    panel 215 in Step S8 is cleared, the internal flag F is unset, and    the end flag EF is set.

In the following part, instances of the process shown in FIG. 19 areexplained, i.e. in case of the user application 237 shown in FIG. 23A.In this case, the initial value of the end flag EF has been set as “1”.

(Process 1)

In Step S0, the LC is set as zero by a timer interruption. In Step S1,“ResetEnd(Toner.Level>Level.High)” is read out from the line of LC=0,the CLC is set as 0, and the LC is set as 1. Through Steps S2, S3 andS4, in Step S5, determined is whether the condition expression“Toner.Level>Level.High” in the ResetEnd statement is satisfied or not.Right after a new toner cartridge is mounted, the condition expressionis satisfied, and consequently, the EF is unset as 0 in Step S6. Here,the threshold value Level.High has been stored in the PROM 213 inadvance as shown in FIG. 20 together with other threshold values such asLevel.Low1, Level.Low2, and the like mentioned below.

Return to Step S1, “If Toner.Level<Level.Low1 {” is read out from theline of LC=1, the CLC is set as 1, and the LC is set as 7. Through StepsS2, S3, S7 and S8, in Step S9, determined is whether the conditionexpression “Toner.Level<Level.Low1” is satisfied or not. The conditionexpression is not satisfied, and therefore, return to Step S1. In StepS1, Null is read out from the line of LC=7, and in Step S2 it isdetermined that the line to be read out does not exist, and then theprocess ends.

(Process 2)

When the next timer interruption takes place, the LC is set as 0 in StepS0. In Step S1, “ResetEnd(Toner.Level>Level.High)” is read out from theline of LC=0, the CLC is set as 0, and the LC is set as 1. Through StepsS2 and S3, in Step S4, it is determined that EF=0, and then return toStep 1. In Step S1, “If Toner.Level<Level.Low1” is read out from theline of LC=1, the CLC is set as 1, and the LC is set as 7. Through StepsS2, S3, S7 and S8, in Step S9, determined is whether the conditionexpression “Toner.Level<Level.Low1” is satisfied or not. The conditionexpression is not satisfied, and therefore, return to Step S1. In StepS1, Null is read out from the line of LC=7, and in Step S2 it isdetermined that the line to be read out does not exist, and then theprocess ends.

Until the condition expression is satisfied, Process 2 is executedrepeatedly.

(Process 3)

As shown in FIG. 22, the remaining amount of toner Toner.Level decreaseswith the passage of time. When the Toner.Level becomes less than thepreset threshold value Level.Low1, the condition expression“Toner.Level<Level.Low1” is satisfied.

In Step S0, the LC is set as 0 by a timer interruption. In Step S1,“ResetEnd(Toner.Level>Level.High)” is read out from the line of LC=0,the CLC is set as 0, and the LC is set as 1. Through Steps S2 and S3, inStep S4, it is determined that EF=0, and then return to Step 1. In StepS1, “If Toner.Level<Level.Low1” is read out from the line of LC=1, theCLC is set as 1, and the LC is set as 7. Through Steps S2, S3, S7 andS8, in Step S9, determined is whether the condition expression“Toner.Level<Level.Low1” is satisfied or not. The condition expressionis satisfied, and therefore, go to Step S10. In Step S10, the LC is setas 2, and return to Step S1. In Step S1, “Button(120, 80, 60, 30,CARTRIDGE ORDER & CrLf & REMAIN & Toner.Level.ToPages & SHEETS) {” isread out from the line of LC=2, the CLC is set as 2, and the LC is setas 7 (i.e. the next line of the close brace in line 6). Through StepsS2, S3 and S7, in Step S8, data to be display the button 240 isgenerated as mentioned above, and the button 240 is displayed on theoperation panel 215 and then the internal flag F is set. If a touch(push-down) operation has not been detected in the area where the button240 is displayed (specified by the arguments 120, 80, 60, 30), it isdetermined that the condition is not satisfied in Step S9, and thenreturn to Step S1. In Step S1, Null is read out from the line of LC=7,and in Step S2, it is determined that the line to be read out does notexist, and then the process ends.

Until a touch (push-down) operation is detected on the area of thebutton 240, Process 3 is executed repeatedly.

(Process 4)

If a touch (push-down) operation is detected on the area of the button240, it is determined that the condition is satisfied in Step S9, andtherefore, in Step S10 the LC is set as 3, and then return to Step S1.In Step S1, “Order(Toner.RFID To DefaultDealer)” is read out from theline of LC=3, the CLC is set as 3, and the LC is set as 4. Through StepsS2, S3, S7 and S11, in Step S12, the line of CLC=3 is processed.Specifically, an HTTP request message is generated and transmitted tothe web server machine 227 as the address “DefaultDealer” (e.g.http://km.com:80 shown in FIG. 20) via the NIC 218 and the Internet 226.The HTTP request message contains the toner cartridge type contained inToner.RFID, and a user ID that does not appear in the Order statement.The request line of this message may be “GET/cgi-bin/order.cgi?UserID=21035&Type=KM102 HTTP/1.0”, for example. Here,as shown in FIG. 20, “UserID=21035” has been stored in the PROM 213 inadvance. “Type=KM102” means the toner cartridge type that is a part ofcontent of Toner.RFID. HTTP messages are transmitted/received in termsof the HTTP processing module 339 and the OS 230.

The web server machine 227 receives this HTTP request message, andstarts a CGI program at the path “/cgi-bin/order.cgi” specified in themessage with an argument which the query string“UserID=21035&Type=KM102” in the message is set to. As a result, asshown in FIG. 26, the order time, the toner cartridge type, a customerID and an estimated shipping date are registered in a table TBL1. Theorder time is the date and time when the order is received. The customerID is the same as the user ID. The estimated shipping date is decidedbased on a state of the inventory that identified from the result ofretrieving an inventory database 229 with a key which the tonercartridge type is set to. A done flag in the table TBL1 has been unsetuntil the shipping, and is set at the shipping. The table TBL1 is linkedto a customer information table TBL2 that contains fields of a customerID, a company name, an address, a name of a person in charge, a name ofa section which the person belongs to, a telephone number, a facsimilenumber, and so on. The table TBL1 and the table TBL2 constitute arelational database.

The web server machine 227 generates an HTTP response message thatcontains the order time, the toner cartridge type, the estimatedshipping date, and transmits the message to the image forming apparatus210. The HTTP response message is generated based on a template file.The image forming apparatus 210 receives the message, and displayscontent of the message on the operation panel 215 as shown in FIG. 21C.

After the aforementioned process for the line of CLC=3 is finished,return to Step S1, and then “End;” is read out from the line of LC=4,the CLC is set as 4, and the LC is set as 7. Through Steps S2, S3, S7and S11, in Step S13, “End;” in the line of CLC=4 is processed.Specifically, the button 240 displayed on the operation panel 215 iscleared, the internal flag F is unset, and the end flag EF is set.

Therefore, until a new toner cartridge is mounted, it is determined thatthe EF is not 0 and the REC is not satisfied in Steps S4 and S5 even ifthe process shown in FIG. 19 is started by a timer interruption, andconsequently, the toner cartridge order button 240 is not displayed onthe operation panel 215, but the order-completed indication is keptdisplaying.

After Process 4, if a new toner cartridge is mounted as shown in FIG.22, the condition in the ResetEnd statement becomes satisfied.Consequently, Process 1 is performed, and through Step S5, the EF isunset as 0 in Step S6, and the order-completed indication on theoperation panel 215 is cleared.

If it is not necessary to order a toner cartridge because a tonercartridge is in the inventory, when the toner cartridge is changed, theMPU 211 reads out the output of the electronic tag reader 223 accordingto a program other than one shown in FIG. 19, and stores the output inthe DRAM 214 as Toner.RFID shown in FIG. 20. In this time, a processsame as Step S13 in FIG. 19 is executed according to the program.Therefore, until “Toner.Level<Level.Low1” is satisfied, the tonercartridge order button 240 is not displayed on the operation panel 215.

As mentioned above, according to Embodiment 3, the user applicationcontains the conditioned reset end statement ResetEnd, and a pair ofattribution information and an Order statement. A user operation to thebutton 240 is detected when a condition in the statement ResetEnd issatisfied according to the language processing program 238. Upondetecting the user operation, the Order statement is executed.Therefore, it is possible to use a non-complex description in the userapplication capable of changing a user interface according to acondition, even if condition statements are nested.

Specifically, it is possible to use a non-complex description in theuser application capable of changing a user interface according to acondition, even if an additional if statement is nested to the conditionstatements.

Further, the button 240 is displayed as an icon on the operation panel215 based on the attribution information “120, 80, 60, 30, CARTRIDGEORDER & CrLf & REMAIN & Toner.Level.ToPages & SHEETS” described in theuser application, and upon detecting a user operation to the button 240,consumable-goods order information is transmitted to the address via theNIC 218 based on the consumable-goods order statement “Order(Toner.RFIDTo DefaultDealer)” described in the user application. Therefore, due toa non-complex description in the user application, a user can orderconsumable goods easily. In addition, consumable goods can be ordered atan adequate timing even if a consuming rate of consumable goodsincreases or decrease sharply contrary to an expectation.

Further, the attribution information on the button 240 contains adescription of a consumption state “REMAIN & Toner.Level.ToPages &SHEETS”, and the detected consumption state is displayed on theoperation panel 215 based on the description. Therefore, it is possibleto order consumable goods at an adequate timing with a simpledescription.

Further, the consumption state is displayed in the indication area “120,80, 60, 30” of the button 240. Therefore, high usability is achieved.

Further, since Step S4 is performed before Step S5, while the end flagEF is set, a condition expression in the reset end statement ResetEnd isnot checked. Therefore, a user operation to the button 240 can bedetected without complex statements in a user application even if thedetected value of the remaining amount of toner is changed due to amechanical vibration.

Further, ordering consumable-goods is displayed on the operation panel215 after the consumable-goods order information is transmitted, andtherefore, other users are prevented from ordering the sameconsumable-goods again by mistake.

Furthermore, the button 240 on the operation panel 215 is deleted afterthe consumable-goods order information is transmitted, and therefore,high usability is achieved and other users are prevented from orderingthe same consumable-goods again by mistake.

Further, the button 240 is deleted according to the end statement Endcontained in the user application, and therefore, in terms of a simpledescription (i.e. End statement), it is possible to delete the button240.

Further, the toner cartridge type is read out from the electronic tagand inserted into the order information automatically rather thanmanually.

FIGS. 23B and 23C show user applications in which an order method isdifferent from one in the user application shown in FIG. 23A.

In the case shown in FIG. 23B, as a cartridge ordering process, “FaxcartridgeOrderFile.pdf to ADDRESSBOOK(dealer1, fax)” is performed withthe FAX module 352 in Step S12 in FIG. 19. According to this statement,content of the file “cartridgeOrderFile.pdf” is transmitted to theaddress. A return value of the function “ADDRESSBOOK(dealer1, fax)” isset to the address. In the address book, a facsimile number and an emailaddress has been registered in a record of each of addresses. Theargument “fax” means that the function returns a facsimile number in therecord specified by the argument “dealer1”.

In the case shown in FIG. 23C, as a cartridge ordering process, “EmailcartridgeOrderFile.pdf to ADDRESSBOOK(dealer1, email)” is performed withthe email module 353 in Step S12 in FIG. 19. According to thisstatement, content of the file “cartridgeOrderFile.pdf” is transmittedto the address. A return value of the function “ADDRESSBOOK(dealer1,email)” is set to the address. The argument “email” means that thefunction returns an email address in the record specified by theargument “dealer1”.

The process shown in FIG. 19 can be applied to user applications withoutrelation to consumable-goods ordering. Instances of the userapplications are shown in FIGS. 24A to 24C.

In the following part, the process of FIG. 19 applied to the userapplication shown in FIG. 24A is explained.

(Process 5)

In Step S0, the LC is set as 0 by a timer interruption. In Step S1,“Button(20, 30, 60, 30, SLIP TRANSMISSION) {” is read out from the lineof LC=0, the CLC is set as 0, and the LC is set as 5. Through Steps S2,S3 and S7, in Step S8, the button 241 shown in FIG. 21B is displayed,and the internal flag F is set. If a touch (push-down) operation has notbeen detected in the area where the button 240 is displayed (specifiedby the arguments 20, 30, 60, 30), it is determined that the condition isnot satisfied in Step S9, and then return to Step S1. In Step S1, Nullis read out from the line of LC=5, and in Step S2, it is determined thatthe line to be read out does not exist, and then the process ends.

Until a touch (push-down) operation is detected on the area of thebutton 241, Process 5 is executed repeatedly.

(Process 6)

If a user puts a document on a flatbed and pushes down the button 241,the condition in Step S9 is satisfied and the LC is set as 1 in StepS10, and then return to Step S1.

In Step S1, “file.pdf=Scan” is read out from the line of LC=1, the CLCis set as 1, and the LC is set as 2. Through Steps S2, S3, S7 and S11,in Step S12, the line of CLC=1 is processed. Specifically, the scanner217 scans an image of the document to generate image data, converts theimage data to the PDF format, and generates a PDF file “file.pdf” thatcontains the converted image data.

Return to Step S1, and “Fax file.pdf to ADDRESSBOOK(HEADQUARTERACCOUNTING DEPARTMENT, fax)” is read out from the line of LC=2, the CLCis set as 2, and the LC is set as 3. Through Steps S2, S3, S7 and S11,in Step S12, the line of CLC=2 is processed. Specifically, content ofthe file “file.pdf” is transmitted to the address that is a return valueof “ADDRESSBOOK(HEADQUARTER ACCOUNTING DEPARTMENT, fax)”.

Return to Step S1, “Email file.pdf to ADDRESSBOOK(TARO SASAKI, email)”is read out from the line of LC=3, the CLC is set as 3, and the LC isset as 5. Through Steps S2, S3, S7 and S11, in Step S12, the line ofCLC=3 is processed. Specifically, content of the file “file.pdf” istransmitted via email to the address that is a return value of“ADDRESSBOOK(TARO SASAKI, email)”. For example, it is possible totransmit a copy of a facsimile document via email to the userhimself/herself who sends the facsimile document.

In Step S1, Null is read out from the line of LC=5, and in Step S2, itis determined that the line to be read out does not exist, and then theprocess ends. The button 241 continues to be displayed on the operationpanel 215.

In case of the user application shown in FIG. 24B, the aforementionedprocess is executed, and after the email is transmitted, the Endstatement is processed, and therefore, in Step S13, the button 241 onthe operation panel 215 is cleared, the internal flag F is unset, andthe end flag EF is set.

In case of the user application shown in FIG. 24C, before the processsame as one of the user application shown in FIG. 24B, in Step S12,“ResetEnd(ICcardID=KM01)” in the line of CLC=1 is processed.Specifically, the IC card reader 222 reads out a user ID and anencrypted password via radio wave from user's IC card 224B. On the otherhand, a user ID and a twice-encrypted password are read out from thePROM 213, the twice-encrypted password is decrypted once, and then theuser ID and the encrypted password from the IC card 224B are verifiedwith the user ID and the once-encrypted password from the PROM 213. Ifboth of the user IDs and both of the encrypted passwords are identical,i.e. if the user who has the user ID “KM01” is authenticatedsuccessfully, the condition in the ResetEnd statement is satisfied inStep S5, and the EF is unset as 0 in Step S6. After the ResetEndstatement, executed is the process same as one of the user applicationshown in FIG. 24B.

If the user authentication is failed, the in Step S5 it is determinedthat the condition in the ResetEnd statement is not satisfied, and then,the process ends. As a result, the button 241 is not displayed on theoperation panel 215.

Therefore, only for valid users, the button 241 is always displayed onthe operation panel 215, and the aforementioned process is executed, andthen the button 241 is deleted when the process is finished. Accordingto such simple user applications, different user interfaces can beestablished for respective users.

The description of the present invention has been presented for purposesof illustration and description, and is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art.

For example, although a multi function peripheral is explained as aninstance of the image forming apparatus in Embodiment 1, the imageforming apparatus may be a printer, a facsimile machine, a scanner, orthe like.

Further, in Embodiment 1, pieces of the service definition data 15 a maybe prepared for respective usecases. Each of the usecases contains aseries of services.

Further, although the service definition data 15 a is described in WSDLin Embodiment 1, the service definition data 15 a may be described inanother language capable of describing as well as WSDL. Further, in theschema data 15 b and the service definition data 15 a, the schema may bedescribed in a language different from XML Schema. In this case, theservice definition data 15 a and the schema data 15 b have to be textdata that can be edited easily.

Further, in Embodiment 1, the service definition data 15 a and/or theschema data 15 b may be stored in a server device accessible via thecomputer network 2, and the multi function peripheral 1 may download anduse the service definition data 15 a and/or the schema data 15 b.

Further, although a multi function peripheral is explained as aninstance of the image forming apparatus in Embodiment 2, the imageforming apparatus may be a printer, a facsimile machine, a scanner, orthe like.

Further, in Embodiment 2, pieces of the service definition data 15 a maybe prepared for respective usecases. Each of the usecases contains aseries of services.

Further, although the service definition data 115 a is described in WSDLin Embodiment 2, the service definition data 115 a may be described inanother language capable of describing as well as WSDL. Further, in theschema data 115 b and the service definition data 115 a, the schema maybe described in a language different from XML Schema. In this case, theservice definition data 115 a and the schema data 115 b have to be textdata that can be edited easily.

Further, in Embodiment 2, the service definition data 115 a and/or theschema data 115 b may be stored in a server device accessible via thecomputer network 102, and the multi function peripheral 101 may downloadand use the service definition data 115 a and/or the schema data 115 b.

Further, in Embodiment 2, the service definition data 115 a and theschema data 115 b may contain attribution information on the displaydevice 111 a such as type, resolution, color type (color or monochrome),and the attribution information may be displayed in the terminal device103 at the customization. For instance, the type of the display device111 a may be a two-raw by two-column liquid crystal display, adot-matrix display, an 8.5 inch full color liquid crystal panel, etc.

Further, in Embodiment 2, an operation command for changing a layout ofbuttons etc. on the screen may be described in the precedure_stringelement. If the command is described, the screen is changed to anotherscreen on which the buttons and so on are displayed in another layoutwhen the button is pushed down.

Further, in Embodiment 2, an operation command described in theprocedure_string element may be the name of a service defined in theservice definition data 115 a. Specifically, syntax definitions of aservice such as scan service provided by the multi function peripheral101 are described in the service definition data 115 a, and when thebutton is operated, a message compatible with the syntax transmits fromthe operation panel 111 to the XML processing unit 122, and the multifunction peripheral 101 operates for the service. Further, in Embodiment2, a series of operation commands may be described in XML in one or morechild elements of the procedure_string element.

Further, in Embodiment 3, a plurality of application programs may beprepared or a plurality of pairs of a condition phrase and a processstatement may be described in an application program. If do so, three ormore buttons can be displayed on the screen shown in FIG. 21B in orderto process daily business.

Further, in Embodiment 3, icons displayed on the operation panel 215 mayhave various kinds of shapes.

Further, in Embodiment 3, an interactive input/output device of acomputer system may be used instead of the operation panel. Theinteractive input/output device (i.e. a remote console) is connected tothe communicating device of the image forming apparatus. In this case,the icon is pushed down by clicking on a mouse of the device.

1. An image forming apparatus that performs one or more servicesaccording to a request, comprising: an internal device that performs aservice; a message processing unit that parses a message according toservice definition data, the service definition data including (a)syntaxdefinitions of an interface part of the service and (b)designation of aprotocol to be used for the service; and a control unit that controlsthe internal device according to a request obtained from a result ofparsing the message by the message processing unit in order to performthe service.
 2. The image forming apparatus according to claim 1 furthercomprising: a receiving unit that receives the message via a computernetwork according to a communication protocol, wherein the messageprocessing unit parses the message received by the receiving unit. 3.The image forming apparatus according to claim 1, wherein the messageprocessing unit generates a message indicating a result of the serviceaccording to the service definition data.
 4. The image forming apparatusaccording to claim 3 further comprising: a receiving unit that receivesa message via a computer network according to a communication protocol,and a transmitting unit that transmits a message via the computernetwork; wherein the message processing unit parses a message receivedby the receiving unit, the message processing unit generates a messageindicating a result of the service performed according to a requestobtained from a result of parsing the message received by the receivingunit, and the transmitting unit transmits the message generated by themessage processing unit.
 5. The image forming apparatus according toclaim 4, wherein the protocol designated in the service definition datais SOAP, the receiving unit receives the message according to HTTP, andthe transmitting unit transmits the message according to HTTP.
 6. Theimage forming apparatus according to claim 1, wherein the servicedefinition data is XML data described in WSDL.
 7. The image formingapparatus according to claim 1, wherein the service definition dataincludes schema data, the schema data includes syntax definitions of themessage to be received or transmitted, and the message processing unitparses the message according to the service definition data and theschema data.
 8. The image forming apparatus according to claim 1,wherein the service definition data includes a reference to schema data,and the message processing unit reads out the schema data with thereference and parses the message according to the service definitiondata and the schema data.
 9. The image forming apparatus according toclaim 7, wherein the service definition data is XML data described inWSDL, and the schema data is XML data described in XML Schema.
 10. Animage forming system comprising: a terminal device connected to acomputer network, and an image forming apparatus that is connected tothe computer network and performs one or more services according to arequest that occurs in the terminal device; wherein the image formingapparatus comprises: a receiving unit that receives a request messagevia the computer network according to a communication protocol; aninternal device that performs the one or more services; a messageprocessing unit that parses the request message according to servicedefinition data and schema data, the service definition data including(a) syntax definitions of an interface part of the service and (b)designation of a protocol to be used for the service, the schema dataincluding syntax definitions of the message; and a control unit thatcontrols the internal device according to a request obtained from aresult of parsing the request message by the message processing unit inorder to perform the service; and the terminal device obtains theservice definition data and/or the schema data from the image formingapparatus, generates and transmits the request message to the imageforming apparatus according to the service definition data and/or theschema data.
 11. The image forming system according to claim 10, whereinthe terminal device distills permissible values of a parameter from theservice definition data and/or the schema data, selects one of thepermissible values as a value of the parameter, and generates therequest message including the value of the parameter.
 12. The imageforming system according to claim 10, wherein the image formingapparatus further comprises a transmitting unit that transmits a messagevia the computer network according to the communication protocol;wherein the message processing unit of the image forming apparatusgenerates a response message indicating a result of the serviceperformed according to a request obtained from a result of parsing therequest message received by the receiving unit, and the transmittingunit of the image forming apparatus transmits the response messagegenerated by the message processing unit, and the terminal devicereceives the response message.
 13. The image forming system according toclaim 12, wherein the protocol designated in the service definition datais SOAP, the receiving unit receives the message according to HTTP, andthe transmitting unit transmits the message according to HTTP.
 14. Theimage forming system according to claim 10, wherein the servicedefinition data is XML data described in WSDL, and the schema data isXML data described in XML Schema.
 15. The image forming system accordingto claim 10, wherein the service definition data includes schema data,the schema data includes syntax definitions of the message to bereceived or transmitted, and the message processing unit parses themessage according to the service definition data and the schema data.16. The image forming system according to claim 10, wherein the servicedefinition data includes a reference to schema data, and the messageprocessing unit reads out the schema data with the reference and parsesthe message according to the service definition data and the schemadata.
 17. The image forming system according to claim 15, wherein theservice definition data is XML data described in WSDL, and the schemadata is XML data described in XML Schema.
 18. An image forming apparatuscomprising: a display device that displays a user interface screen; adata storage device that stores user interface data containingattributions of components in the user interface screen, the userinterface data described as text data; and a UI data parsing unit thatidentifies attributions of the components with parsing the userinterface data, and causes the display device to display the userinterface screen that reflects the attributions of the components. 19.The image forming apparatus according to claim 18 further comprising: amessage processing unit that parses a message according to servicedefinition data, the service definition data including (a) syntaxdefinitions of an interface part of an editing service of the userinterface data and (b) designation of a protocol to be used for theservice; and a control unit that performs the editing service accordingto a request obtained from a result of parsing the message by themessage processing unit.
 20. The image forming apparatus according toclaim 19 further comprising a receiving unit that receives the messagevia a computer network according to a communication protocol, whereinthe message processing unit parses the message received by the receivingunit.
 21. The image forming apparatus according to claim 20, wherein theprotocol designated in the service definition data is SOAP, and thereceiving unit receives the message according to HTTP.
 22. The imageforming apparatus according to claim 19, wherein the service definitiondata is XML data described in WSDL.
 23. The image forming apparatusaccording to claim 19, wherein the service definition data includesschema data, the schema data includes syntax definitions of the messageto be received or transmitted, and the message processing unit parsesthe message according to the service definition data and the schemadata.
 24. The image forming apparatus according to claim 19, wherein theuser interface data and the message are described in XML, and thecontrol unit updates the user interface data with an XML text of theattributions of the components distilled by the message processing unit.25. An image forming system comprising: an image forming apparatusconnected to a computer network, and a terminal device connected to thecomputer network; wherein the image forming apparatus comprises: adisplay device that displays a user interface screen; a data storagedevice that stores user interface data containing attributions ofcomponents in the user interface screen, the user interface datadescribed as text data; a UI data parsing unit that identifiesattributions of the components with parsing the user interface data, andcauses the display device to display the user interface screen thatreflects the attributions of the components; a receiving unit thatreceives the message via the computer network according to acommunication protocol; a message processing unit that parses a messageaccording to service definition data, the service definition dataincluding (a) syntax definitions of an interface part of an editingservice of the user interface data and (b) designation of a protocol tobe used for the service; and a control unit that performs the editingservice according to a request obtained from a result of parsing themessage by the message processing unit; and the terminal devicecomprises a transmitting unit that transmits the message via thecomputer network according to a communication protocol.
 26. The imageforming system according to claim 25, wherein the data storage devicestores schema data including syntax definitions of the message, theterminal device further comprises a schema data obtaining unit thatobtains a part or all of the schema data from the image formingapparatus and identifies one or more items in the attributions of thecomponents with the part or all of the schema data, and the transmittingunit transmits the message to set one or more values to a part or all ofthe one or more items identified by the schema data obtaining unit. 27.The image forming system according to claim 25, wherein the data storagedevice stores schema data including syntax definitions of the message,the terminal device further comprises a schema data obtaining unit thatobtains a part or all of the schema data from the image formingapparatus and identifies one or more permissible values on theattributions of the components with the part or all of the schema data,and the transmitting unit transmits the message to set a value selectedfrom the one or more permissible values to one of the attributions. 28.The image forming system according to claim 26, wherein the userinterface data and the message are described in XML, the schema data isdescribed in XML Schema, and the control unit updates the user interfacedata with an XML text of the attributions of the components distilled bythe message processing unit.
 29. The image forming system according toclaim 25, wherein the data storage device stores template filescontaining respective default data of the user interface screen, and thetransmitting unit selects one of the template files and transmits themessage to set default data in the selected template file as data of oneof user interface screens in the user interface data.